Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a65c3f52bddfa0afeb46663e338fc4d30ee61904003c7d4f8cd60ac261987a08

Tx prefix hash: 7bfc2c27218666e55939d6e43d711d9615211a90e724e634de949a77df265a5b
Tx public key: ab58dc49930c074d00389a52f942f391a155b6cdbc7691905347f326e19f6a8a
Timestamp: 1695956629 Timestamp [UCT]: 2023-09-29 03:03:49 Age [y:d:h:m:s]: 01:154:01:32:51
Block: 858433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371128 RingCT/type: yes/0
Extra: 01ab58dc49930c074d00389a52f942f391a155b6cdbc7691905347f326e19f6a8a0211000000024b8f5122000000000000000000

1 output(s) for total of 0.878324835000 dcy

stealth address amount amount idx
00: f2f30f07e0b03e4b510b22ab68995d353fbd1a0b4b110c0709604eee583b2023 0.878324835000 1312607 of 0

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": 858443, "vin": [ { "gen": { "height": 858433 } } ], "vout": [ { "amount": 878324835, "target": { "key": "f2f30f07e0b03e4b510b22ab68995d353fbd1a0b4b110c0709604eee583b2023" } } ], "extra": [ 1, 171, 88, 220, 73, 147, 12, 7, 77, 0, 56, 154, 82, 249, 66, 243, 145, 161, 85, 182, 205, 188, 118, 145, 144, 83, 71, 243, 38, 225, 159, 106, 138, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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