Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6158b3f8038ab04c57803d29c194d0b7ef058b2af116fb7575eaf920a284e75f

Tx prefix hash: 4a526c8b17e9e57ccdfb83bb266f0183a7541bfba1cc0f6abad2ea11a583fe17
Tx public key: 568edaf352ec15b8efde146e7ce5d90ec1fe0a7dbe5ba562f2180375b7a2402c
Timestamp: 1725015743 Timestamp [UCT]: 2024-08-30 11:02:23 Age [y:d:h:m:s]: 00:206:21:50:06
Block: 1099140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147719 RingCT/type: yes/0
Extra: 01568edaf352ec15b8efde146e7ce5d90ec1fe0a7dbe5ba562f2180375b7a2402c02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2e3e74b748db11093b79c38bf504de81dc5de8a28ce6849335142899c450694 0.600000000000 1575067 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": 1099150, "vin": [ { "gen": { "height": 1099140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2e3e74b748db11093b79c38bf504de81dc5de8a28ce6849335142899c450694" } } ], "extra": [ 1, 86, 142, 218, 243, 82, 236, 21, 184, 239, 222, 20, 110, 124, 229, 217, 14, 193, 254, 10, 125, 190, 91, 165, 98, 242, 24, 3, 117, 183, 162, 64, 44, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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