Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9678cd4f374b8225a2a242da5bc97953ff734e53ae4b51b6910a0b1e13905bbe

Tx prefix hash: 2ca0650502d307f21b9ff9e43d4c3031a4677cd0bdaaef907f7e667bbe083b2b
Tx public key: 2178968c74e066e9ca48e9fd4f69e16c247fe1d44f2ba8658cc83943c80a3746
Timestamp: 1737497789 Timestamp [UCT]: 2025-01-21 22:16:29 Age [y:d:h:m:s]: 00:334:02:54:29
Block: 1202419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236397 RingCT/type: yes/0
Extra: 012178968c74e066e9ca48e9fd4f69e16c247fe1d44f2ba8658cc83943c80a3746021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56de7cb24ae23cd7f8d825f8c069472029260fe6ceac0671929c26d696c64230 0.600000000000 1689082 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": 1202429, "vin": [ { "gen": { "height": 1202419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56de7cb24ae23cd7f8d825f8c069472029260fe6ceac0671929c26d696c64230" } } ], "extra": [ 1, 33, 120, 150, 140, 116, 224, 102, 233, 202, 72, 233, 253, 79, 105, 225, 108, 36, 127, 225, 212, 79, 43, 168, 101, 140, 200, 57, 67, 200, 10, 55, 70, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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