Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fda356c3474fff0d70e1a8d77a58300333e4b7b17c6b9a019bcb845e7c0f76d

Tx prefix hash: 6643377ee1a100e0a346f7c936c1873e3cfeae8f7a1f0e13149201cb671a0141
Tx public key: 16355201a1685c699e907e5e7c638e288d71f51540527060a1a267f30c24da75
Timestamp: 1754004122 Timestamp [UCT]: 2025-07-31 23:22:02 Age [y:d:h:m:s]: 00:184:10:44:16
Block: 1337638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130617 RingCT/type: yes/0
Extra: 0116355201a1685c699e907e5e7c638e288d71f51540527060a1a267f30c24da75021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 392f91eb16f9a2b8f82a94d1b8192281a867a9a5bda5b4c784f8916c688a5e2d 0.600000000000 1825443 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": 1337648, "vin": [ { "gen": { "height": 1337638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "392f91eb16f9a2b8f82a94d1b8192281a867a9a5bda5b4c784f8916c688a5e2d" } } ], "extra": [ 1, 22, 53, 82, 1, 161, 104, 92, 105, 158, 144, 126, 94, 124, 99, 142, 40, 141, 113, 245, 21, 64, 82, 112, 96, 161, 162, 103, 243, 12, 36, 218, 117, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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