Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 766e5de298c71977b3964f70464132a3b0a0702418f0ea5e7920677b8a4ca100

Tx prefix hash: 4c4bc68ee66c66c69424fb85a057cf594c82f276de50982351ce3c2061968511
Tx public key: 00d5b574e8a4d4a9a9c14cf116fefbab86d1125d27a847698b2496fee1c5f6f0
Timestamp: 1707734686 Timestamp [UCT]: 2024-02-12 10:44:46 Age [y:d:h:m:s]: 00:276:17:53:06
Block: 955861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198142 RingCT/type: yes/0
Extra: 0100d5b574e8a4d4a9a9c14cf116fefbab86d1125d27a847698b2496fee1c5f6f002110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce7238886ac077c051f8d589631a6b9ec80a9ffdf4c6a76bbec9451586f55ba0 0.600000000000 1415161 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": 955871, "vin": [ { "gen": { "height": 955861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce7238886ac077c051f8d589631a6b9ec80a9ffdf4c6a76bbec9451586f55ba0" } } ], "extra": [ 1, 0, 213, 181, 116, 232, 164, 212, 169, 169, 193, 76, 241, 22, 254, 251, 171, 134, 209, 18, 93, 39, 168, 71, 105, 139, 36, 150, 254, 225, 197, 246, 240, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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