Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e881517c8da9307fd0bc41f1250ad464d86490de851dc0f9f603dc75dd075e1

Tx prefix hash: 01f6a7ec8b8cea23c0ce30f57e973f6db6077a8f66dd06913ff1dc9a61747cf7
Tx public key: 8ab2fea3c16497f5e0fb0cdc7ce25d68b24d6d91eb24ca4f2dab1bb9ee07277b
Timestamp: 1699325648 Timestamp [UCT]: 2023-11-07 02:54:08 Age [y:d:h:m:s]: 01:145:08:28:06
Block: 886159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365072 RingCT/type: yes/0
Extra: 018ab2fea3c16497f5e0fb0cdc7ce25d68b24d6d91eb24ca4f2dab1bb9ee07277b021100000001faf35c9c000000000000000000

1 output(s) for total of 0.710865397000 dcy

stealth address amount amount idx
00: 1e12059c0b16e038486c258c02a5c6b8107b97aa6371155f332a757b8b354aa2 0.710865397000 1341968 of 0

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": 886169, "vin": [ { "gen": { "height": 886159 } } ], "vout": [ { "amount": 710865397, "target": { "key": "1e12059c0b16e038486c258c02a5c6b8107b97aa6371155f332a757b8b354aa2" } } ], "extra": [ 1, 138, 178, 254, 163, 193, 100, 151, 245, 224, 251, 12, 220, 124, 226, 93, 104, 178, 77, 109, 145, 235, 36, 202, 79, 45, 171, 27, 185, 238, 7, 39, 123, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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