Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3088e36028b97c7a61b8f5a8ad4bfe12e5a9c7b1158a8c23e5036e3a0ef4d48e

Tx prefix hash: 4284182ba1df9c46abd51738727ca74cbbfea5ec0045062465af63660b4c5d24
Tx public key: 5a0421733fd80aad911819078b49383367182914fc3cd8fbd4942f86f4e524e3
Timestamp: 1763421530 Timestamp [UCT]: 2025-11-17 23:18:50 Age [y:d:h:m:s]: 00:010:06:30:45
Block: 1414412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7356 RingCT/type: yes/0
Extra: 015a0421733fd80aad911819078b49383367182914fc3cd8fbd4942f86f4e524e302110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aa36cbf9629d6b801038c8a4dcde691a0b916d238c8dca07ba0f72f8bb57278 0.600000000000 1902901 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": 1414422, "vin": [ { "gen": { "height": 1414412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aa36cbf9629d6b801038c8a4dcde691a0b916d238c8dca07ba0f72f8bb57278" } } ], "extra": [ 1, 90, 4, 33, 115, 63, 216, 10, 173, 145, 24, 25, 7, 139, 73, 56, 51, 103, 24, 41, 20, 252, 60, 216, 251, 212, 148, 47, 134, 244, 229, 36, 227, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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