Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 360d9d6366f0c171b481ddbbe904a845f7888dd1b6013f42a07d43d8788b5b0f

Tx prefix hash: 4c8f7e2360e5f7a0b561178569cfc14a27d85dbdb106f39c959cfb52b30ad02f
Tx public key: 42f4e25a879cf637acb095b322acd1fa579034dcf6e399e4dbd10fc95ee2b14f
Timestamp: 1710865358 Timestamp [UCT]: 2024-03-19 16:22:38 Age [y:d:h:m:s]: 01:259:07:07:57
Block: 981849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444032 RingCT/type: yes/0
Extra: 0142f4e25a879cf637acb095b322acd1fa579034dcf6e399e4dbd10fc95ee2b14f0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b38943d1fab9f319a56cac2ba0fcf949fffc9d3d5c651fadd91dad13b3ca8b87 0.600000000000 1441948 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": 981859, "vin": [ { "gen": { "height": 981849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b38943d1fab9f319a56cac2ba0fcf949fffc9d3d5c651fadd91dad13b3ca8b87" } } ], "extra": [ 1, 66, 244, 226, 90, 135, 156, 246, 55, 172, 176, 149, 179, 34, 172, 209, 250, 87, 144, 52, 220, 246, 227, 153, 228, 219, 209, 15, 201, 94, 226, 177, 79, 2, 17, 0, 0, 0, 4, 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