Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d4b226e17be7ea9e77dac2629a8a535a28217a0115b6334db436ac63f444630

Tx prefix hash: 855cd59fa483c7dc881a6e269645137a82caded3dd5b63d9d59acb2bf6890a06
Tx public key: cb6ed9793f92a02392918ddad0b69213ec3f80159990d80a3dee5219549daf96
Timestamp: 1720783995 Timestamp [UCT]: 2024-07-12 11:33:15 Age [y:d:h:m:s]: 00:256:14:20:04
Block: 1064071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183290 RingCT/type: yes/0
Extra: 01cb6ed9793f92a02392918ddad0b69213ec3f80159990d80a3dee5219549daf9602110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b6c0c7f80e00737a676a733a0203b5c96cae3c4a79bf5b5e6de14f7dd24e13c 0.600000000000 1534594 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": 1064081, "vin": [ { "gen": { "height": 1064071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b6c0c7f80e00737a676a733a0203b5c96cae3c4a79bf5b5e6de14f7dd24e13c" } } ], "extra": [ 1, 203, 110, 217, 121, 63, 146, 160, 35, 146, 145, 141, 218, 208, 182, 146, 19, 236, 63, 128, 21, 153, 144, 216, 10, 61, 238, 82, 25, 84, 157, 175, 150, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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