Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 868b0ae5edb98d69b1c4fde32c6ba0d4aa06b715787a92c8709c719ac303c9fe

Tx prefix hash: 7fab0083e067e36245af0be111712455c6cbfd9538f733d9f41aaa363677ac2a
Tx public key: 51107c1735d17f8b2ce7339aca16ad0a2c84538231679049c01ab275d4c773d9
Timestamp: 1721148389 Timestamp [UCT]: 2024-07-16 16:46:29 Age [y:d:h:m:s]: 01:113:11:27:10
Block: 1067095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339581 RingCT/type: yes/0
Extra: 0151107c1735d17f8b2ce7339aca16ad0a2c84538231679049c01ab275d4c773d902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a3de4dbdc2e083b6746f86da10aef807e9138cf787ef2d0ea61f32675f3566d 0.600000000000 1537814 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": 1067105, "vin": [ { "gen": { "height": 1067095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a3de4dbdc2e083b6746f86da10aef807e9138cf787ef2d0ea61f32675f3566d" } } ], "extra": [ 1, 81, 16, 124, 23, 53, 209, 127, 139, 44, 231, 51, 154, 202, 22, 173, 10, 44, 132, 83, 130, 49, 103, 144, 73, 192, 26, 178, 117, 212, 199, 115, 217, 2, 17, 0, 0, 0, 4, 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