Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 937cf693e0d27a9edabe8de9af673ab6c6583ae33287e1edf021f2b57f4810c1

Tx prefix hash: 19ffaeca6dd4f8e938d1b62203ef3ce69fe4c7cb69a62906027d390bd4b381ae
Tx public key: 0d2c7aee8b0edd99bf6ffd901f61989eff1d4dddaf945b8f1b3c131ba7a21baa
Timestamp: 1749954347 Timestamp [UCT]: 2025-06-15 02:25:47 Age [y:d:h:m:s]: 00:159:10:52:39
Block: 1305231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111734 RingCT/type: yes/0
Extra: 010d2c7aee8b0edd99bf6ffd901f61989eff1d4dddaf945b8f1b3c131ba7a21baa02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e9f8ad0b778435ca58aac6d015136bb34760ebc988c0f631ddf5d0d5d0101cc 0.600000000000 1792830 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": 1305241, "vin": [ { "gen": { "height": 1305231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e9f8ad0b778435ca58aac6d015136bb34760ebc988c0f631ddf5d0d5d0101cc" } } ], "extra": [ 1, 13, 44, 122, 238, 139, 14, 221, 153, 191, 111, 253, 144, 31, 97, 152, 158, 255, 29, 77, 221, 175, 148, 91, 143, 27, 60, 19, 27, 167, 162, 27, 170, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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