Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 36e64ff0d9bdba770f17d1228512a948e900ba089ca10aad78ee151d3ec09b2b

Tx prefix hash: 999f0e9f5687b2c21c0702aac654660a3bde275d7d3e546e681433d376a96aa5
Tx public key: c099edcbc355eec9ab5573b68906141a2ce5ba9a49a841a5ebb06e85e581c590
Timestamp: 1734709162 Timestamp [UCT]: 2024-12-20 15:39:22 Age [y:d:h:m:s]: 00:019:10:06:11
Block: 1179408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13870 RingCT/type: yes/0
Extra: 01c099edcbc355eec9ab5573b68906141a2ce5ba9a49a841a5ebb06e85e581c5900211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 577fb82a27261d718e827b2abbb801bafef5966f7869855d24b6ae6f10803d0a 0.600000000000 1665803 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1179418, "vin": [ { "gen": { "height": 1179408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "577fb82a27261d718e827b2abbb801bafef5966f7869855d24b6ae6f10803d0a" } } ], "extra": [ 1, 192, 153, 237, 203, 195, 85, 238, 201, 171, 85, 115, 182, 137, 6, 20, 26, 44, 229, 186, 154, 73, 168, 65, 165, 235, 176, 110, 133, 229, 129, 197, 144, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8