Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 854e06b8e965e202609e9bccd5693dfbdf4ababed93e60781e549f584b4004b1

Tx prefix hash: aa9becf04874b743e3624c835df92c1f21c7fb5a077de535d70695eb422e636a
Tx public key: f735a058a6e86af7724f106efb80003a92a7b7df440e24ba5e63a0b2d7373543
Timestamp: 1754944797 Timestamp [UCT]: 2025-08-11 20:39:57 Age [y:d:h:m:s]: 00:147:01:06:30
Block: 1345018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104454 RingCT/type: yes/0
Extra: 01f735a058a6e86af7724f106efb80003a92a7b7df440e24ba5e63a0b2d737354302110000000bb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab55c2df8ca18d24b7285ca85de0d3120d2ba3eb65f85cacb2b811c772f2308f 0.600000000000 1832907 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": 1345028, "vin": [ { "gen": { "height": 1345018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab55c2df8ca18d24b7285ca85de0d3120d2ba3eb65f85cacb2b811c772f2308f" } } ], "extra": [ 1, 247, 53, 160, 88, 166, 232, 106, 247, 114, 79, 16, 110, 251, 128, 0, 58, 146, 167, 183, 223, 68, 14, 36, 186, 94, 99, 160, 178, 215, 55, 53, 67, 2, 17, 0, 0, 0, 11, 178, 247, 132, 196, 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