Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad5341395335f934168636e1a5116d24c6406455454c27057e3fa26da877a2ca

Tx prefix hash: 466f75704ccf7ee347adf04d770b998c2829ce461a3e8d427d77e9286310a4b7
Tx public key: 61ac45ccdb9ef912235e27c403b7e618f1eceba5414aeceb687dcd1d1b33a2b4
Timestamp: 1657366496 Timestamp [UCT]: 2022-07-09 11:34:56 Age [y:d:h:m:s]: 02:294:08:34:01
Block: 539998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 731531 RingCT/type: yes/0
Extra: 0161ac45ccdb9ef912235e27c403b7e618f1eceba5414aeceb687dcd1d1b33a2b402110000001b4da16a3a000000000000000000

1 output(s) for total of 9.971548573000 dcy

stealth address amount amount idx
00: 35add529329d9573d00fd941a1d4e8b6b04ae339c7e629317dce436e0cc0f29c 9.971548573000 970179 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": 540008, "vin": [ { "gen": { "height": 539998 } } ], "vout": [ { "amount": 9971548573, "target": { "key": "35add529329d9573d00fd941a1d4e8b6b04ae339c7e629317dce436e0cc0f29c" } } ], "extra": [ 1, 97, 172, 69, 204, 219, 158, 249, 18, 35, 94, 39, 196, 3, 183, 230, 24, 241, 236, 235, 165, 65, 74, 236, 235, 104, 125, 205, 29, 27, 51, 162, 180, 2, 17, 0, 0, 0, 27, 77, 161, 106, 58, 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