Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12a2f450d539abf996bb25be6d02ca8a17a33f1d4463274d23aa3ad2e8d7056e

Tx prefix hash: 06074caea544b89b4c7e99a361de822554c2f7b186d0cfcc31b8d451e5a75cc7
Tx public key: 21b834a6d430d2b28757aedcc9d3ac403dac35bb0c7c6f4a1250dd1b5d3e9906
Timestamp: 1729384524 Timestamp [UCT]: 2024-10-20 00:35:24 Age [y:d:h:m:s]: 00:070:17:51:26
Block: 1135349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50547 RingCT/type: yes/0
Extra: 0121b834a6d430d2b28757aedcc9d3ac403dac35bb0c7c6f4a1250dd1b5d3e9906021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8f0c8f15740df6d855e886a6f22b60a17f290059b8427c50c89e074b2af7463 0.600000000000 1618686 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": 1135359, "vin": [ { "gen": { "height": 1135349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8f0c8f15740df6d855e886a6f22b60a17f290059b8427c50c89e074b2af7463" } } ], "extra": [ 1, 33, 184, 52, 166, 212, 48, 210, 178, 135, 87, 174, 220, 201, 211, 172, 64, 61, 172, 53, 187, 12, 124, 111, 74, 18, 80, 221, 27, 93, 62, 153, 6, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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