Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 262ec6616cfb9a2f0c838347de0877abeeca5916d5cbcce4f3ac691c37624b1c

Tx prefix hash: 275b4522207d329d315593805680cbb4bd75958daa41290ce0f67b0645463b0b
Tx public key: fa57a0e0bf9beea459dde22de8351853c62e83e4c06a9aa5be571c355a36281a
Timestamp: 1634056832 Timestamp [UCT]: 2021-10-12 16:40:32 Age [y:d:h:m:s]: 03:149:21:27:17
Block: 351779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 884535 RingCT/type: yes/0
Extra: 01fa57a0e0bf9beea459dde22de8351853c62e83e4c06a9aa5be571c355a36281a02110000000dfdc024ec000000000000000000

1 output(s) for total of 41.918966135000 dcy

stealth address amount amount idx
00: 413a22e6d60ce2d72807f9e223f5d4f333d85a5bc37b4083de16f23d410a01de 41.918966135000 719249 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": 351789, "vin": [ { "gen": { "height": 351779 } } ], "vout": [ { "amount": 41918966135, "target": { "key": "413a22e6d60ce2d72807f9e223f5d4f333d85a5bc37b4083de16f23d410a01de" } } ], "extra": [ 1, 250, 87, 160, 224, 191, 155, 238, 164, 89, 221, 226, 45, 232, 53, 24, 83, 198, 46, 131, 228, 192, 106, 154, 165, 190, 87, 28, 53, 90, 54, 40, 26, 2, 17, 0, 0, 0, 13, 253, 192, 36, 236, 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