Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72ad1f1edef431a96d1c82d1421e470d8d199f4f8f9989b4bd56dd93ea9630ac

Tx prefix hash: 3c9bb09b67ca7b8ff139065e02370aecffa1529822c0accfc48b7a86b0f04364
Tx public key: c38520df89265a8f6f9549d2fc98eb9676cac68573d1a375283a335d0d0a9c55
Timestamp: 1710130540 Timestamp [UCT]: 2024-03-11 04:15:40 Age [y:d:h:m:s]: 01:006:06:54:13
Block: 975743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265489 RingCT/type: yes/0
Extra: 01c38520df89265a8f6f9549d2fc98eb9676cac68573d1a375283a335d0d0a9c550211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a71f42a1b03c873002615016b0fedbca971ad05f9986b9b4242cb62a30372e0c 0.600000000000 1435716 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": 975753, "vin": [ { "gen": { "height": 975743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a71f42a1b03c873002615016b0fedbca971ad05f9986b9b4242cb62a30372e0c" } } ], "extra": [ 1, 195, 133, 32, 223, 137, 38, 90, 143, 111, 149, 73, 210, 252, 152, 235, 150, 118, 202, 198, 133, 115, 209, 163, 117, 40, 58, 51, 93, 13, 10, 156, 85, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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