Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75bc01caa1cf832a950c1e8721dbf58ffc70ffdef666f7871342ff8ef19506e8

Tx prefix hash: d732aaa36953d7a83f03185505f47bbcf4c643149f4b5503e16ec9a6c807a157
Tx public key: 33736ddd3ef9ee793ca1d180a898f28d07df437b77a5ee0e92e343b59884a0a1
Timestamp: 1576283332 Timestamp [UCT]: 2019-12-14 00:28:52 Age [y:d:h:m:s]: 05:322:21:53:00
Block: 26754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1374754 RingCT/type: yes/0
Extra: 0133736ddd3ef9ee793ca1d180a898f28d07df437b77a5ee0e92e343b59884a0a10211000000169159db1e000000000000000000

1 output(s) for total of 500.442009057000 dcy

stealth address amount amount idx
00: 5ad8a58914cf24a9845f1b19d2f4d7f8140b59bcf2a562d333ad48debee7d346 500.442009057000 44234 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": 26764, "vin": [ { "gen": { "height": 26754 } } ], "vout": [ { "amount": 500442009057, "target": { "key": "5ad8a58914cf24a9845f1b19d2f4d7f8140b59bcf2a562d333ad48debee7d346" } } ], "extra": [ 1, 51, 115, 109, 221, 62, 249, 238, 121, 60, 161, 209, 128, 168, 152, 242, 141, 7, 223, 67, 123, 119, 165, 238, 14, 146, 227, 67, 181, 152, 132, 160, 161, 2, 17, 0, 0, 0, 22, 145, 89, 219, 30, 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