Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1c1a54d136f488bf572ab1abd727ff7633a7ffb9204fd40246c334353fc13dc

Tx prefix hash: b46433310f2cb51e82cc94c2b07b7f85b8084db51c34243f2679b6f5a42624f0
Tx public key: f7167e5d7bb77f9b5a852ee2dbb461b911c47b26ef3d8972dc8dd31e91f7ac43
Timestamp: 1740921920 Timestamp [UCT]: 2025-03-02 13:25:20 Age [y:d:h:m:s]: 00:312:02:23:33
Block: 1230541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220884 RingCT/type: yes/0
Extra: 01f7167e5d7bb77f9b5a852ee2dbb461b911c47b26ef3d8972dc8dd31e91f7ac43021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 099284e29826d0e70df41dd18153e5199053f6d50cc16338295a12244a77fbb3 0.600000000000 1717440 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": 1230551, "vin": [ { "gen": { "height": 1230541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "099284e29826d0e70df41dd18153e5199053f6d50cc16338295a12244a77fbb3" } } ], "extra": [ 1, 247, 22, 126, 93, 123, 183, 127, 155, 90, 133, 46, 226, 219, 180, 97, 185, 17, 196, 123, 38, 239, 61, 137, 114, 220, 141, 211, 30, 145, 247, 172, 67, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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