Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fcc94222adf6c16c6736c15df8f95edf473d1a2e3b22c01badf0285e63bb9b2

Tx prefix hash: ffcd70daf24954ce1c6a5b92ba05e120f610c8f6d09dfaf9627df1879261fe04
Tx public key: e160c7fc7bf5556f1dc343583d48a708c1d8cfd3f392ab32a76bb039a4045614
Timestamp: 1717357936 Timestamp [UCT]: 2024-06-02 19:52:16 Age [y:d:h:m:s]: 01:157:09:46:51
Block: 1035656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371070 RingCT/type: yes/0
Extra: 01e160c7fc7bf5556f1dc343583d48a708c1d8cfd3f392ab32a76bb039a404561402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa5bf7099c89154b1903094a3dc90fad88a8f0360105fec85352f3700d861556 0.600000000000 1504179 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": 1035666, "vin": [ { "gen": { "height": 1035656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa5bf7099c89154b1903094a3dc90fad88a8f0360105fec85352f3700d861556" } } ], "extra": [ 1, 225, 96, 199, 252, 123, 245, 85, 111, 29, 195, 67, 88, 61, 72, 167, 8, 193, 216, 207, 211, 243, 146, 171, 50, 167, 107, 176, 57, 164, 4, 86, 20, 2, 17, 0, 0, 0, 2, 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