Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de22605389aededef69b0f2e674df14b07196a4e11a410044aec9b46a73f31ec

Tx prefix hash: 2a170cde4fafceb958d874e26e6c81f1c2effa64037b6c75b1ad44da40658239
Tx public key: 3d76cf17c6586aea23a8a1b1403f9e1e34eeada1b580405fe9ea2bf735c679f2
Timestamp: 1747074938 Timestamp [UCT]: 2025-05-12 18:35:38 Age [y:d:h:m:s]: 00:192:09:52:26
Block: 1281484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135216 RingCT/type: yes/0
Extra: 013d76cf17c6586aea23a8a1b1403f9e1e34eeada1b580405fe9ea2bf735c679f202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9142ca6442f2982c66ae714d2617cbd00518dd1d997ef969732d378fd0fb31f5 0.600000000000 1768883 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": 1281494, "vin": [ { "gen": { "height": 1281484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9142ca6442f2982c66ae714d2617cbd00518dd1d997ef969732d378fd0fb31f5" } } ], "extra": [ 1, 61, 118, 207, 23, 198, 88, 106, 234, 35, 168, 161, 177, 64, 63, 158, 30, 52, 238, 173, 161, 181, 128, 64, 95, 233, 234, 43, 247, 53, 198, 121, 242, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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