Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2afbd62b7c58f905558fea37bbf206b513ad76b890fd592cf3c627d34567d200

Tx prefix hash: ebf222dafae3baf8e4d568922c083d69767684f2ad1e935e538448be29b6dd18
Tx public key: 74f5206f56cc5e2ebac1ba817bf274f890bab0f4d6f97f479cd809f7f5d8ee6c
Timestamp: 1765679729 Timestamp [UCT]: 2025-12-14 02:35:29 Age [y:d:h:m:s]: 00:049:07:16:06
Block: 1433115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35134 RingCT/type: yes/0
Extra: 0174f5206f56cc5e2ebac1ba817bf274f890bab0f4d6f97f479cd809f7f5d8ee6c021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50ebff4c032829c4643a80cd83dbd18e328656a905512ef4e5fd40221af221f2 0.600000000000 1921894 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": 1433125, "vin": [ { "gen": { "height": 1433115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50ebff4c032829c4643a80cd83dbd18e328656a905512ef4e5fd40221af221f2" } } ], "extra": [ 1, 116, 245, 32, 111, 86, 204, 94, 46, 186, 193, 186, 129, 123, 242, 116, 248, 144, 186, 176, 244, 214, 249, 127, 71, 156, 216, 9, 247, 245, 216, 238, 108, 2, 17, 0, 0, 0, 9, 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