Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 208749188d2291adfb1e6f412971ba79d02fc4d8488a2ff93c105684d2fc93bd

Tx prefix hash: dc44d62200656fd7406108df186e8eebb25347011429e0cbb63f7c281b8fca0a
Tx public key: 87b9a3da3f7a210a9ef79de5a54c507a8bf8f0a42d37500181b72cae3e198104
Timestamp: 1730877866 Timestamp [UCT]: 2024-11-06 07:24:26 Age [y:d:h:m:s]: 00:133:12:36:32
Block: 1147648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95281 RingCT/type: yes/0
Extra: 0187b9a3da3f7a210a9ef79de5a54c507a8bf8f0a42d37500181b72cae3e198104021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 726c4e523d515b15fbe6941ef0bf8d8a2e37f725c9f4c25999fe55a26273e4d8 0.600000000000 1632347 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": 1147658, "vin": [ { "gen": { "height": 1147648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "726c4e523d515b15fbe6941ef0bf8d8a2e37f725c9f4c25999fe55a26273e4d8" } } ], "extra": [ 1, 135, 185, 163, 218, 63, 122, 33, 10, 158, 247, 157, 229, 165, 76, 80, 122, 139, 248, 240, 164, 45, 55, 80, 1, 129, 183, 44, 174, 62, 25, 129, 4, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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