Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9350e61331bef41c46b5a467b9367e09b46ea8dc05c857abc0436396ee478e73

Tx prefix hash: 8b922198861a16d4b95af802db59a6b8992515d4cc7859732bc9ea1205a52dc3
Tx public key: be361e3059cd4ef4614598bf3e64a0cbc17290412d5eacf34a2d6b9b49203df7
Timestamp: 1750071908 Timestamp [UCT]: 2025-06-16 11:05:08 Age [y:d:h:m:s]: 00:157:20:39:26
Block: 1306195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110604 RingCT/type: yes/0
Extra: 01be361e3059cd4ef4614598bf3e64a0cbc17290412d5eacf34a2d6b9b49203df7021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb7ebf7b83bd4a353caca01689d1e6f85f6d928e83bbb313e717a79fcef7d292 0.600000000000 1793798 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": 1306205, "vin": [ { "gen": { "height": 1306195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb7ebf7b83bd4a353caca01689d1e6f85f6d928e83bbb313e717a79fcef7d292" } } ], "extra": [ 1, 190, 54, 30, 48, 89, 205, 78, 244, 97, 69, 152, 191, 62, 100, 160, 203, 193, 114, 144, 65, 45, 94, 172, 243, 74, 45, 107, 155, 73, 32, 61, 247, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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