Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ead6b26e6d582313507eb613a9722e45e706c689cc7d98fc70b0dcabc08a2b8

Tx prefix hash: d4c6bd12a142e6308088572e7c697a13430fa221e2ea51d4afdac6f36186b837
Tx public key: d4ca21e6900dc31224e21a98e49853e156bbff8a06d2afa745fe7c6f4cb516fe
Timestamp: 1711540814 Timestamp [UCT]: 2024-03-27 12:00:14 Age [y:d:h:m:s]: 01:222:16:40:44
Block: 987454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417807 RingCT/type: yes/0
Extra: 01d4ca21e6900dc31224e21a98e49853e156bbff8a06d2afa745fe7c6f4cb516fe02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8589e40f7a44b740bb6d0be979bfe01acf360c3194f39ef662cd4fd630bf7b6c 0.600000000000 1447703 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": 987464, "vin": [ { "gen": { "height": 987454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8589e40f7a44b740bb6d0be979bfe01acf360c3194f39ef662cd4fd630bf7b6c" } } ], "extra": [ 1, 212, 202, 33, 230, 144, 13, 195, 18, 36, 226, 26, 152, 228, 152, 83, 225, 86, 187, 255, 138, 6, 210, 175, 167, 69, 254, 124, 111, 76, 181, 22, 254, 2, 17, 0, 0, 0, 5, 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