Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81fa44856bd6eba339ecf0e8c8d23307106da49ea15f8369933178820ae0212a

Tx prefix hash: 0a86a497179cd330891d0312eb1a606cc827dc2eda9f1faf3000258f9b0dd707
Tx public key: 3aef4b6e83e7a0cb29d9d6356f87e3257008e88d7664752198a4b91cc7970fe6
Timestamp: 1703615292 Timestamp [UCT]: 2023-12-26 18:28:12 Age [y:d:h:m:s]: 01:144:04:00:32
Block: 921716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364173 RingCT/type: yes/0
Extra: 013aef4b6e83e7a0cb29d9d6356f87e3257008e88d7664752198a4b91cc7970fe60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ae0e85ebc33251ea0823e9fa4e8094978e6a0e419c6bed50ca33f8ccf0e1c6f 0.600000000000 1379410 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": 921726, "vin": [ { "gen": { "height": 921716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ae0e85ebc33251ea0823e9fa4e8094978e6a0e419c6bed50ca33f8ccf0e1c6f" } } ], "extra": [ 1, 58, 239, 75, 110, 131, 231, 160, 203, 41, 217, 214, 53, 111, 135, 227, 37, 112, 8, 232, 141, 118, 100, 117, 33, 152, 164, 185, 28, 199, 151, 15, 230, 2, 17, 0, 0, 0, 1, 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