Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb21e9dadc4c76c533f9f7767f3ebceb5f364c28b7b45d22bebc675ab1121ec4

Tx prefix hash: 8c34a7fdf83257c21c8ffece6c36a40de935c9a506f04c0be30550a49e51a511
Tx public key: a14ff96fc47bd5aaee9bc2c95dbaae239e17c334c52296b0bd9824e5cac984d9
Timestamp: 1761417081 Timestamp [UCT]: 2025-10-25 18:31:21 Age [y:d:h:m:s]: 00:073:16:09:05
Block: 1397807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52747 RingCT/type: yes/0
Extra: 01a14ff96fc47bd5aaee9bc2c95dbaae239e17c334c52296b0bd9824e5cac984d9021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 715917815a4418e4096d7e1c6f024797a6ea376003ac58c573f68383de85dafd 0.600000000000 1886098 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": 1397817, "vin": [ { "gen": { "height": 1397807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "715917815a4418e4096d7e1c6f024797a6ea376003ac58c573f68383de85dafd" } } ], "extra": [ 1, 161, 79, 249, 111, 196, 123, 213, 170, 238, 155, 194, 201, 93, 186, 174, 35, 158, 23, 195, 52, 197, 34, 150, 176, 189, 152, 36, 229, 202, 201, 132, 217, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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