Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa05cf30649e501d0bfd0e66e5ab13a95f7bd6e01e6b4c6718341fd3ef0243bc

Tx prefix hash: 4c7938eb7c78c7d797053bc140a400a431cdb722825c87280c161b0ee1080839
Tx public key: bc1073a987e4ca23432eb3717c92fe5f73e09e1a0fa64cc6a85a17618830d1e6
Timestamp: 1728809641 Timestamp [UCT]: 2024-10-13 08:54:01 Age [y:d:h:m:s]: 00:081:04:06:16
Block: 1130599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58006 RingCT/type: yes/0
Extra: 01bc1073a987e4ca23432eb3717c92fe5f73e09e1a0fa64cc6a85a17618830d1e602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07f561ceb2c1ac21ad24f82f9f3b42145df796cf3f1a01787aa7b27e234c241c 0.600000000000 1613476 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": 1130609, "vin": [ { "gen": { "height": 1130599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07f561ceb2c1ac21ad24f82f9f3b42145df796cf3f1a01787aa7b27e234c241c" } } ], "extra": [ 1, 188, 16, 115, 169, 135, 228, 202, 35, 67, 46, 179, 113, 124, 146, 254, 95, 115, 224, 158, 26, 15, 166, 76, 198, 168, 90, 23, 97, 136, 48, 209, 230, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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