Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ae8c2708ed628ef60558c012b022c7d01f186973b3b45d2aeaaf7ab7644d09

Tx prefix hash: 92e86574e167e6121e2c50320c1f1bb315b76c5eb145208bea977a045893ee55
Tx public key: be2a2bdd1b83ad65c0cb99d6099937d3a1fe9ad0963c96838d2e96a8bacb14e8
Timestamp: 1717305383 Timestamp [UCT]: 2024-06-02 05:16:23 Age [y:d:h:m:s]: 00:287:04:17:10
Block: 1035228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205242 RingCT/type: yes/0
Extra: 01be2a2bdd1b83ad65c0cb99d6099937d3a1fe9ad0963c96838d2e96a8bacb14e802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe7be082537025b6c3f3e32476e36153ac13eb68b71228a056adbeb02bc8428c 0.600000000000 1503749 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": 1035238, "vin": [ { "gen": { "height": 1035228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe7be082537025b6c3f3e32476e36153ac13eb68b71228a056adbeb02bc8428c" } } ], "extra": [ 1, 190, 42, 43, 221, 27, 131, 173, 101, 192, 203, 153, 214, 9, 153, 55, 211, 161, 254, 154, 208, 150, 60, 150, 131, 141, 46, 150, 168, 186, 203, 20, 232, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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