Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 563f2e83544927cd5c70536453aa404396fc5cd945a5e2b2114f9070b2d0a854

Tx prefix hash: 7497ac14cd950ff3ee0d53437b1ab19caafc4fd309cefea51d01d896f7ae11a9
Tx public key: b9e1f46ae36581ef16d998b9ec5ad7a7733b50ef221810603309c5d20437f22a
Timestamp: 1754028023 Timestamp [UCT]: 2025-08-01 06:00:23 Age [y:d:h:m:s]: 00:016:12:30:32
Block: 1337839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10833 RingCT/type: yes/0
Extra: 01b9e1f46ae36581ef16d998b9ec5ad7a7733b50ef221810603309c5d20437f22a021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08a97ca99af6523b356f0f4131d86a87769cb16515a8b6e2d85d9f8b9e7a76c6 0.600000000000 1825646 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": 1337849, "vin": [ { "gen": { "height": 1337839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08a97ca99af6523b356f0f4131d86a87769cb16515a8b6e2d85d9f8b9e7a76c6" } } ], "extra": [ 1, 185, 225, 244, 106, 227, 101, 129, 239, 22, 217, 152, 185, 236, 90, 215, 167, 115, 59, 80, 239, 34, 24, 16, 96, 51, 9, 197, 210, 4, 55, 242, 42, 2, 17, 0, 0, 0, 5, 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