Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d22ceaf2a40c3340788928b0fdcdbcc875031bb9b007ede99e2aca27ec8b89b

Tx prefix hash: 5191fadfabb5fd1ecf0c06bdcac0c18acabf80c4827163abf6f686045325b851
Tx public key: a4fb593390425f27d207f764c46d05766c164f7b5b7f6fd6bef5e945a8877b33
Timestamp: 1747630583 Timestamp [UCT]: 2025-05-19 04:56:23 Age [y:d:h:m:s]: 00:141:21:52:21
Block: 1286079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99071 RingCT/type: yes/0
Extra: 01a4fb593390425f27d207f764c46d05766c164f7b5b7f6fd6bef5e945a8877b3302110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa5bb0072517dd63b5482fd9928b539ad4f8164769a902e2dc6c601c0044fba8 0.600000000000 1773544 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": 1286089, "vin": [ { "gen": { "height": 1286079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa5bb0072517dd63b5482fd9928b539ad4f8164769a902e2dc6c601c0044fba8" } } ], "extra": [ 1, 164, 251, 89, 51, 144, 66, 95, 39, 210, 7, 247, 100, 196, 109, 5, 118, 108, 22, 79, 123, 91, 127, 111, 214, 190, 245, 233, 69, 168, 135, 123, 51, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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