Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 718dbff4feb0e556958a07f85305b6bf6b64a90a06d169efec1ca194ea05df85

Tx prefix hash: c47fb2d2b86bb0fc3f881f96e9fa77642e2e32fbb3fa9fad57c9c1b1fba8e2b1
Tx public key: 0d7aa06d40821c29d8a25af24253a184404d8a5c245d71cce1687fc010d04986
Timestamp: 1715883374 Timestamp [UCT]: 2024-05-16 18:16:14 Age [y:d:h:m:s]: 01:145:19:48:47
Block: 1023421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362787 RingCT/type: yes/0
Extra: 010d7aa06d40821c29d8a25af24253a184404d8a5c245d71cce1687fc010d049860211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d1a0e5e2b24acc2eed8346d220ed85b990c8bed7c7c1c002e9d5e1f9e6195f9 0.600000000000 1488388 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": 1023431, "vin": [ { "gen": { "height": 1023421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d1a0e5e2b24acc2eed8346d220ed85b990c8bed7c7c1c002e9d5e1f9e6195f9" } } ], "extra": [ 1, 13, 122, 160, 109, 64, 130, 28, 41, 216, 162, 90, 242, 66, 83, 161, 132, 64, 77, 138, 92, 36, 93, 113, 204, 225, 104, 127, 192, 16, 208, 73, 134, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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