Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9956e097a31e586584a1e83e62cab5fbf2187f2628cfa36d070c964b4abfe4d7

Tx prefix hash: 9265025f4ab4029402f00adb31bdc6c94d5b232db55cc99faf4e3ef5cce9ca77
Tx public key: a9c6f74b805b74f71360bea8f68646401250a5af1fadfe5225d36f3cbdc12682
Timestamp: 1746883122 Timestamp [UCT]: 2025-05-10 13:18:42 Age [y:d:h:m:s]: 00:265:08:49:52
Block: 1279897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187279 RingCT/type: yes/0
Extra: 01a9c6f74b805b74f71360bea8f68646401250a5af1fadfe5225d36f3cbdc126820211000000099f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 433a6872cdf84a1dca3251cf23358b7ffb2cf2f4bb0acb8c1cb72d088fab4d28 0.600000000000 1767280 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": 1279907, "vin": [ { "gen": { "height": 1279897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "433a6872cdf84a1dca3251cf23358b7ffb2cf2f4bb0acb8c1cb72d088fab4d28" } } ], "extra": [ 1, 169, 198, 247, 75, 128, 91, 116, 247, 19, 96, 190, 168, 246, 134, 70, 64, 18, 80, 165, 175, 31, 173, 254, 82, 37, 211, 111, 60, 189, 193, 38, 130, 2, 17, 0, 0, 0, 9, 159, 159, 230, 140, 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