Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b791957a3d2e1de16cb8dc9456edb579e3158a484b68b9d52c5f7346c7689bd

Tx prefix hash: f3f940ee5ab4e185eeddcc01c568b5969d8150aeeaabfc43ea147168cbc9e851
Tx public key: 7c814a56732241ff3ed343550fc300447bba4cc4f0bd2c5a2641c224ffa9715f
Timestamp: 1764392909 Timestamp [UCT]: 2025-11-29 05:08:29 Age [y:d:h:m:s]: 00:063:14:21:52
Block: 1422471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45348 RingCT/type: yes/0
Extra: 017c814a56732241ff3ed343550fc300447bba4cc4f0bd2c5a2641c224ffa9715f02110000000bd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd81953e83d1e51b9dfa22f1e4cff2f70c3e457af2a6d7618d8093dc0c0813c9 0.600000000000 1911036 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": 1422481, "vin": [ { "gen": { "height": 1422471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd81953e83d1e51b9dfa22f1e4cff2f70c3e457af2a6d7618d8093dc0c0813c9" } } ], "extra": [ 1, 124, 129, 74, 86, 115, 34, 65, 255, 62, 211, 67, 85, 15, 195, 0, 68, 123, 186, 76, 196, 240, 189, 44, 90, 38, 65, 194, 36, 255, 169, 113, 95, 2, 17, 0, 0, 0, 11, 214, 225, 157, 124, 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