Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b16781ced667f0da7737da3920ef69d825c9f0374b3cd41b4e60240e22f6fcc7

Tx prefix hash: ef722eda52a18135f58c6f5ed5bb1c753ef98694ef5726908780fbcd594d8b27
Tx public key: 5c4acc9b2385a0b0565854d76ee4b5e9c10c5c23796c5b3f40212403a8b3bb79
Timestamp: 1722046246 Timestamp [UCT]: 2024-07-27 02:10:46 Age [y:d:h:m:s]: 00:083:04:03:01
Block: 1074516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59578 RingCT/type: yes/0
Extra: 015c4acc9b2385a0b0565854d76ee4b5e9c10c5c23796c5b3f40212403a8b3bb7902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7093da640caf898abc3c717fc1587db7ed5e255e752c66d10a900a34457d3e24 0.600000000000 1547029 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": 1074526, "vin": [ { "gen": { "height": 1074516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7093da640caf898abc3c717fc1587db7ed5e255e752c66d10a900a34457d3e24" } } ], "extra": [ 1, 92, 74, 204, 155, 35, 133, 160, 176, 86, 88, 84, 215, 110, 228, 181, 233, 193, 12, 92, 35, 121, 108, 91, 63, 64, 33, 36, 3, 168, 179, 187, 121, 2, 17, 0, 0, 0, 6, 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