Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0d03065741978e2fb042b4d443b0b040a9480c7630d9c4499c168decf6e56ef

Tx prefix hash: 63b544627000fae09b6b2fd23e671c94e2f0c22f3b9169bac3cee3c2fb8c2c5e
Tx public key: 6f47f85ed4bcff95358f508f14548ff7156c4aaae75b850fbf1ed36b8e6bc5dc
Timestamp: 1722782937 Timestamp [UCT]: 2024-08-04 14:48:57 Age [y:d:h:m:s]: 00:202:07:42:47
Block: 1080619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144463 RingCT/type: yes/0
Extra: 016f47f85ed4bcff95358f508f14548ff7156c4aaae75b850fbf1ed36b8e6bc5dc02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9355734412ed17cb582c8cfa4f9858cd0cd29397e81386657ca29629e7120c8e 0.600000000000 1554054 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": 1080629, "vin": [ { "gen": { "height": 1080619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9355734412ed17cb582c8cfa4f9858cd0cd29397e81386657ca29629e7120c8e" } } ], "extra": [ 1, 111, 71, 248, 94, 212, 188, 255, 149, 53, 143, 80, 143, 20, 84, 143, 247, 21, 108, 74, 170, 231, 91, 133, 15, 191, 30, 211, 107, 142, 107, 197, 220, 2, 17, 0, 0, 0, 1, 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