Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 623d937e35c4fd7287b5f479f8252ba9669664c7a3ba4a7e29a6fe7b10654172

Tx prefix hash: e1107f15c9fa139cac2f3ff38b7a371149c628eac762318b54d2b4bfc8eb80da
Tx public key: a52bacd40f4d8639aabae6d401870db609840bc79050c316e021274cc00a564a
Timestamp: 1749697523 Timestamp [UCT]: 2025-06-12 03:05:23 Age [y:d:h:m:s]: 00:150:00:47:44
Block: 1303167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104939 RingCT/type: yes/0
Extra: 01a52bacd40f4d8639aabae6d401870db609840bc79050c316e021274cc00a564a02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7e81eaf2eddaea9a08bf8e1d93964a428ef0cb37efc0e42528e0f5aa1a09e1f 0.600000000000 1790742 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": 1303177, "vin": [ { "gen": { "height": 1303167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7e81eaf2eddaea9a08bf8e1d93964a428ef0cb37efc0e42528e0f5aa1a09e1f" } } ], "extra": [ 1, 165, 43, 172, 212, 15, 77, 134, 57, 170, 186, 230, 212, 1, 135, 13, 182, 9, 132, 11, 199, 144, 80, 195, 22, 224, 33, 39, 76, 192, 10, 86, 74, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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