Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cc8ca9d122fd50cf6aa5d90643d6e3a82755d2f45537439676eaeeca2845d2e

Tx prefix hash: d634f02b69298e56643764861d2ffc52b5638c56a4730b573043bca251a4011c
Tx public key: 7a39f12bb8654b980178e4406e05f728031f417ba4fb8f72451a9efe5597e57a
Timestamp: 1746404397 Timestamp [UCT]: 2025-05-05 00:19:57 Age [y:d:h:m:s]: 00:197:17:30:32
Block: 1275934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139038 RingCT/type: yes/0
Extra: 017a39f12bb8654b980178e4406e05f728031f417ba4fb8f72451a9efe5597e57a02110000000d1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2f12fc5b7ac6c583a6f697ac658b1745d82938729ae1db9e159a7b163b13080 0.600000000000 1763249 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": 1275944, "vin": [ { "gen": { "height": 1275934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2f12fc5b7ac6c583a6f697ac658b1745d82938729ae1db9e159a7b163b13080" } } ], "extra": [ 1, 122, 57, 241, 43, 184, 101, 75, 152, 1, 120, 228, 64, 110, 5, 247, 40, 3, 31, 65, 123, 164, 251, 143, 114, 69, 26, 158, 254, 85, 151, 229, 122, 2, 17, 0, 0, 0, 13, 31, 144, 81, 122, 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