Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 672a001b3b3a073188a230feb2f6fcfc53105d8dcdc813b5b728a986393e630e

Tx prefix hash: b1d8afd9b1285578673fa0d842e48337c21646ba6a9da3057750ac050d6d5fc2
Tx public key: 640232d2ae249957f2e8254a09ca16c719ebe3b883297d8384ef2c02b803752e
Timestamp: 1726290316 Timestamp [UCT]: 2024-09-14 05:05:16 Age [y:d:h:m:s]: 00:060:08:16:25
Block: 1109700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43148 RingCT/type: yes/0
Extra: 01640232d2ae249957f2e8254a09ca16c719ebe3b883297d8384ef2c02b803752e02110000000b91e13c04000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 9fc8ac925ada3f44d4fcfbe4e2ad37b3ed1be6f1bc071199e4c32eeb8ff38d4f 0.608000000000 1588047 of 0

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": 1109710, "vin": [ { "gen": { "height": 1109700 } } ], "vout": [ { "amount": 608000000, "target": { "key": "9fc8ac925ada3f44d4fcfbe4e2ad37b3ed1be6f1bc071199e4c32eeb8ff38d4f" } } ], "extra": [ 1, 100, 2, 50, 210, 174, 36, 153, 87, 242, 232, 37, 74, 9, 202, 22, 199, 25, 235, 227, 184, 131, 41, 125, 131, 132, 239, 44, 2, 184, 3, 117, 46, 2, 17, 0, 0, 0, 11, 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