Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a275d385e0fd4edd346fc057ed1439ef5081a646cb7b79cc3096aca04021d05b

Tx prefix hash: 8d060e5f80ea7390fff748496f6ab42f5a65a542b047d560fd0e9f9beb8b81ab
Tx public key: 3ef26b2cb40459732bdd144ac4e2772bf0f84cf2cf7a8a4729efc4d090637651
Timestamp: 1760165766 Timestamp [UCT]: 2025-10-11 06:56:06 Age [y:d:h:m:s]: 00:035:16:27:23
Block: 1387432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25555 RingCT/type: yes/0
Extra: 013ef26b2cb40459732bdd144ac4e2772bf0f84cf2cf7a8a4729efc4d09063765102110000000297baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9e75a2089c8c7c85fd572dca1f0fb637e47c7c551b46ecf2f416247e1c49f3c 0.600000000000 1875619 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": 1387442, "vin": [ { "gen": { "height": 1387432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9e75a2089c8c7c85fd572dca1f0fb637e47c7c551b46ecf2f416247e1c49f3c" } } ], "extra": [ 1, 62, 242, 107, 44, 180, 4, 89, 115, 43, 221, 20, 74, 196, 226, 119, 43, 240, 248, 76, 242, 207, 122, 138, 71, 41, 239, 196, 208, 144, 99, 118, 81, 2, 17, 0, 0, 0, 2, 151, 186, 249, 34, 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