Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef094c3df5869e8e5c350adeb2cb28f9130c79beb606398a20ee5cd20c1e1cfb

Tx prefix hash: 58e0ed617209630e0d3fad5c0e1524458b379bb96ad76a044d62028ad71006de
Tx public key: 6d1c4f4ada326f01f8e50ffb77165261f2e6552cd46ddca135d84f3cabca0e65
Timestamp: 1726618992 Timestamp [UCT]: 2024-09-18 00:23:12 Age [y:d:h:m:s]: 00:194:01:20:21
Block: 1112424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138511 RingCT/type: yes/0
Extra: 016d1c4f4ada326f01f8e50ffb77165261f2e6552cd46ddca135d84f3cabca0e6502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 963fb58ca6a14dcf856021a70a4ff61940e7446e09fdc6bddee1dda9d3c8f38a 0.600000000000 1591741 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": 1112434, "vin": [ { "gen": { "height": 1112424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "963fb58ca6a14dcf856021a70a4ff61940e7446e09fdc6bddee1dda9d3c8f38a" } } ], "extra": [ 1, 109, 28, 79, 74, 218, 50, 111, 1, 248, 229, 15, 251, 119, 22, 82, 97, 242, 230, 85, 44, 212, 109, 220, 161, 53, 216, 79, 60, 171, 202, 14, 101, 2, 17, 0, 0, 0, 7, 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