Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb64b92ce7ca4b5a88c86a02cec0e5607c53e03746cc9e5e967762ed9ac71450

Tx prefix hash: b09e3b4b38c1ea60375deb7cd29afcfdf7a8d2eb6f1374f7a71e8284d4529451
Tx public key: ca7e647300b92a9fafe78998c09ac1316e73b028cdc09e25ceb8c390dd40e824
Timestamp: 1714142810 Timestamp [UCT]: 2024-04-26 14:46:50 Age [y:d:h:m:s]: 00:255:22:34:36
Block: 1009001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183191 RingCT/type: yes/0
Extra: 01ca7e647300b92a9fafe78998c09ac1316e73b028cdc09e25ceb8c390dd40e82402110000000318ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b17ceec4fa3afaf788d3a95b4db06a64b9b0ea21b87bc475a5653dbb3c77e5c 0.600000000000 1470537 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": 1009011, "vin": [ { "gen": { "height": 1009001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b17ceec4fa3afaf788d3a95b4db06a64b9b0ea21b87bc475a5653dbb3c77e5c" } } ], "extra": [ 1, 202, 126, 100, 115, 0, 185, 42, 159, 175, 231, 137, 152, 192, 154, 193, 49, 110, 115, 176, 40, 205, 192, 158, 37, 206, 184, 195, 144, 221, 64, 232, 36, 2, 17, 0, 0, 0, 3, 24, 236, 144, 96, 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