Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40d237e6c073b5208dc4c941e4d2a5acb8583dc8819a82356b25f328ef8109bf

Tx prefix hash: 03d7c049639a197eed08ffa77495f36960198d0e624b25c6e65e422ff9a9fd3d
Tx public key: 37d9f0b75a75d8386edd1d7edf556d67b9528aebe9eb4ac9baa0a2274bcd6242
Timestamp: 1711199446 Timestamp [UCT]: 2024-03-23 13:10:46 Age [y:d:h:m:s]: 00:339:18:03:00
Block: 984618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242871 RingCT/type: yes/0
Extra: 0137d9f0b75a75d8386edd1d7edf556d67b9528aebe9eb4ac9baa0a2274bcd62420211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 654a08d77173962336797e26ca76ebcb1b9614327c68eddd46f7c417cf3341e2 0.600000000000 1444789 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": 984628, "vin": [ { "gen": { "height": 984618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "654a08d77173962336797e26ca76ebcb1b9614327c68eddd46f7c417cf3341e2" } } ], "extra": [ 1, 55, 217, 240, 183, 90, 117, 216, 56, 110, 221, 29, 126, 223, 85, 109, 103, 185, 82, 138, 235, 233, 235, 74, 201, 186, 160, 162, 39, 75, 205, 98, 66, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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