Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f5db4464f69ed6fd6f6d4173c8af5d33e418a64f30860ac510cb590c3c966f8

Tx prefix hash: 5538904152bb91a53253314fec91fa43a1398ef89407dd87da8c63a11234ab05
Tx public key: f0c7416f79c4e8bee56dbe1badc251f92c4475422f8d64f6e81b665f8e431974
Timestamp: 1679027866 Timestamp [UCT]: 2023-03-17 04:37:46 Age [y:d:h:m:s]: 01:301:20:20:20
Block: 718769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476627 RingCT/type: yes/0
Extra: 01f0c7416f79c4e8bee56dbe1badc251f92c4475422f8d64f6e81b665f8e4319740211000000025029cbac000000000000000000

1 output(s) for total of 2.549293353000 dcy

stealth address amount amount idx
00: e4ebebef473a1ffad90c10b16f07c0c88e90e881d82edde39cfb558a5927c4b7 2.549293353000 1163458 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": 718779, "vin": [ { "gen": { "height": 718769 } } ], "vout": [ { "amount": 2549293353, "target": { "key": "e4ebebef473a1ffad90c10b16f07c0c88e90e881d82edde39cfb558a5927c4b7" } } ], "extra": [ 1, 240, 199, 65, 111, 121, 196, 232, 190, 229, 109, 190, 27, 173, 194, 81, 249, 44, 68, 117, 66, 47, 141, 100, 246, 232, 27, 102, 95, 142, 67, 25, 116, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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