Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae57f72a859c76b26ea6185be5d3d00905453a59abfc515b478d1da6c63f3187

Tx prefix hash: b8d555223acdf2ef2ef6bb941176c8e5afaedeafb3bd0272fd2d0e07bbd94f1a
Tx public key: 57704b0ccb636113f67d3c979caa5049ae80a0f269a6203c3c01a7cd48f7b7cc
Timestamp: 1718418065 Timestamp [UCT]: 2024-06-15 02:21:05 Age [y:d:h:m:s]: 00:223:10:42:37
Block: 1044444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159859 RingCT/type: yes/0
Extra: 0157704b0ccb636113f67d3c979caa5049ae80a0f269a6203c3c01a7cd48f7b7cc02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e671225da049fcce097c02d016f157880bbcad97e4f9ff5361d4f5be764290aa 0.600000000000 1513755 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": 1044454, "vin": [ { "gen": { "height": 1044444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e671225da049fcce097c02d016f157880bbcad97e4f9ff5361d4f5be764290aa" } } ], "extra": [ 1, 87, 112, 75, 12, 203, 99, 97, 19, 246, 125, 60, 151, 156, 170, 80, 73, 174, 128, 160, 242, 105, 166, 32, 60, 60, 1, 167, 205, 72, 247, 183, 204, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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