Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f3e4d0909d9c01b4114d506e61688999c397579a90870a019b6c1f0117890be

Tx prefix hash: 2efa24ef2a9df9cbb1244f7fb6d5dce79922f267fb0480f0b2ea8e1b9897e98e
Tx public key: c0198855ebf1d81e6b8951952bfdda12c9be8a5c83ff68c55a8da5528d852fe9
Timestamp: 1706621462 Timestamp [UCT]: 2024-01-30 13:31:02 Age [y:d:h:m:s]: 01:308:05:28:35
Block: 946622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479135 RingCT/type: yes/0
Extra: 01c0198855ebf1d81e6b8951952bfdda12c9be8a5c83ff68c55a8da5528d852fe90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e45695211da72ddcf2bc4477ff88c60c77314097282242c055cc0b7f7cdd242e 0.600000000000 1404956 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": 946632, "vin": [ { "gen": { "height": 946622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e45695211da72ddcf2bc4477ff88c60c77314097282242c055cc0b7f7cdd242e" } } ], "extra": [ 1, 192, 25, 136, 85, 235, 241, 216, 30, 107, 137, 81, 149, 43, 253, 218, 18, 201, 190, 138, 92, 131, 255, 104, 197, 90, 141, 165, 82, 141, 133, 47, 233, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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