Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd2e2e1b7c0234fecac92b2e8c9297a818acfc48c9d701ca23c16462ae04dfe5

Tx prefix hash: d6e6a453318c0a2c00696dafecd3dac4a3b96bb95c80701233caf690f78be857
Tx public key: 630c66a84d902073d7a87e2f9a26f11c8e8f7e4aed301437d12aa350567aaa2e
Timestamp: 1729332071 Timestamp [UCT]: 2024-10-19 10:01:11 Age [y:d:h:m:s]: 00:003:07:31:35
Block: 1134919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2342 RingCT/type: yes/0
Extra: 01630c66a84d902073d7a87e2f9a26f11c8e8f7e4aed301437d12aa350567aaa2e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 823a491122751bb1a3969b3f987d7c9164a59203613b2b1ed9335aef60a13182 0.600000000000 1618246 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": 1134929, "vin": [ { "gen": { "height": 1134919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "823a491122751bb1a3969b3f987d7c9164a59203613b2b1ed9335aef60a13182" } } ], "extra": [ 1, 99, 12, 102, 168, 77, 144, 32, 115, 215, 168, 126, 47, 154, 38, 241, 28, 142, 143, 126, 74, 237, 48, 20, 55, 209, 42, 163, 80, 86, 122, 170, 46, 2, 17, 0, 0, 0, 5, 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