Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471547e39f6990e70aca30df04df5eb3350ef10e4aec55d12c0632b3245973df

Tx prefix hash: d1e8bdc1bb2a1c886bc720747d66f64459532c30736ba1875ae487665fb1f575
Tx public key: 3b3052d93c954ea44e5f80047895553b0525d114a9d38057a90e8035845d0d45
Timestamp: 1718096192 Timestamp [UCT]: 2024-06-11 08:56:32 Age [y:d:h:m:s]: 00:281:13:20:20
Block: 1041781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201216 RingCT/type: yes/0
Extra: 013b3052d93c954ea44e5f80047895553b0525d114a9d38057a90e8035845d0d45021100000005d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 441b9bce2969e6aff2f5fe58d42e22e358e3fc6f072e9f8d17e9f26354c4af46 0.600000000000 1510538 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": 1041791, "vin": [ { "gen": { "height": 1041781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "441b9bce2969e6aff2f5fe58d42e22e358e3fc6f072e9f8d17e9f26354c4af46" } } ], "extra": [ 1, 59, 48, 82, 217, 60, 149, 78, 164, 78, 95, 128, 4, 120, 149, 85, 59, 5, 37, 209, 20, 169, 211, 128, 87, 169, 14, 128, 53, 132, 93, 13, 69, 2, 17, 0, 0, 0, 5, 215, 73, 245, 17, 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