Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa6a3f7de98a09b9e68b8c2d1601f5d996d5b7160b8f97bf0e7f45802c3f79fa

Tx prefix hash: 2fbcf3f4e9e8651cae38e031750728457fc30b2ba91a8c47c4bc5bb0c86f90a9
Tx public key: 46d1a7f63e5ceb8ed068676cd8f69099986f064d80994edb5ca5eeeb7fc7e0cf
Timestamp: 1696706453 Timestamp [UCT]: 2023-10-07 19:20:53 Age [y:d:h:m:s]: 01:190:15:15:04
Block: 864644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397288 RingCT/type: yes/0
Extra: 0146d1a7f63e5ceb8ed068676cd8f69099986f064d80994edb5ca5eeeb7fc7e0cf02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.837674958000 dcy

stealth address amount amount idx
00: c5387d56a4693cca0719ef6891d767bc4d336d074ac7b17f4eb8051e76287ed7 0.837674958000 1319164 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": 864654, "vin": [ { "gen": { "height": 864644 } } ], "vout": [ { "amount": 837674958, "target": { "key": "c5387d56a4693cca0719ef6891d767bc4d336d074ac7b17f4eb8051e76287ed7" } } ], "extra": [ 1, 70, 209, 167, 246, 62, 92, 235, 142, 208, 104, 103, 108, 216, 246, 144, 153, 152, 111, 6, 77, 128, 153, 78, 219, 92, 165, 238, 235, 127, 199, 224, 207, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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