Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 440e0b3114738be8abf1f067ead91d86d13d2ff751ddb1eb4ad361882ff6da05

Tx prefix hash: 618c506efc779c00af4a45c19e1be5bfbe1da4a29afd34ab4d778ca9896e9c6a
Tx public key: 23350812a2eeb3b7c342e7041ac9027a49e9b01e76f08fae17295329246edc1e
Timestamp: 1754567025 Timestamp [UCT]: 2025-08-07 11:43:45 Age [y:d:h:m:s]: 00:106:12:42:56
Block: 1342110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75197 RingCT/type: yes/0
Extra: 0123350812a2eeb3b7c342e7041ac9027a49e9b01e76f08fae17295329246edc1e02110000000fb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e91c9d3c68b405d3c055d5e8153c50b2f82e95f03bb921634a58b5510f498398 0.600000000000 1829939 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": 1342120, "vin": [ { "gen": { "height": 1342110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e91c9d3c68b405d3c055d5e8153c50b2f82e95f03bb921634a58b5510f498398" } } ], "extra": [ 1, 35, 53, 8, 18, 162, 238, 179, 183, 195, 66, 231, 4, 26, 201, 2, 122, 73, 233, 176, 30, 118, 240, 143, 174, 23, 41, 83, 41, 36, 110, 220, 30, 2, 17, 0, 0, 0, 15, 178, 247, 132, 196, 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