Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95349239bc1d056e7058b8cf4ea256e7ff917d1aa951051fe312227ecc1b9017

Tx prefix hash: 1aa97565471a34ce52864eb81ef1f190ca9e8cfd6c6ae598e6a90dbf46852212
Tx public key: e2f5c3bf223448342b11098c935affe0e0a20db901db047d8a5a104c65e52ae0
Timestamp: 1715258488 Timestamp [UCT]: 2024-05-09 12:41:28 Age [y:d:h:m:s]: 00:264:11:13:44
Block: 1018256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189013 RingCT/type: yes/0
Extra: 01e2f5c3bf223448342b11098c935affe0e0a20db901db047d8a5a104c65e52ae00211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ad0e166de26c2a00e0b8f4eac47672c249e2b5be51524daf8ff8dbf4929ac1b 0.600000000000 1482045 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": 1018266, "vin": [ { "gen": { "height": 1018256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ad0e166de26c2a00e0b8f4eac47672c249e2b5be51524daf8ff8dbf4929ac1b" } } ], "extra": [ 1, 226, 245, 195, 191, 34, 52, 72, 52, 43, 17, 9, 140, 147, 90, 255, 224, 224, 162, 13, 185, 1, 219, 4, 125, 138, 90, 16, 76, 101, 229, 42, 224, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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