Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3e05e12870b1a6427dbb4ff75b6596b8dbc107a3ffd340ad6a68659d3ae7517

Tx prefix hash: eb15eb078893b42fe64a40dd89e16d4f3975a5aad3766f52e2bec37ab40751dc
Tx public key: b8f278f3315dc349788cbd20574b0ad42e4f4c896873db80dc7a88b02891f2be
Timestamp: 1726170070 Timestamp [UCT]: 2024-09-12 19:41:10 Age [y:d:h:m:s]: 00:201:18:08:25
Block: 1108706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144030 RingCT/type: yes/0
Extra: 01b8f278f3315dc349788cbd20574b0ad42e4f4c896873db80dc7a88b02891f2be021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ae031ac3e3b50a2a83dc3f5f0a89ff60b8719582089300925674c8e13d082d4 0.600000000000 1586695 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": 1108716, "vin": [ { "gen": { "height": 1108706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ae031ac3e3b50a2a83dc3f5f0a89ff60b8719582089300925674c8e13d082d4" } } ], "extra": [ 1, 184, 242, 120, 243, 49, 93, 195, 73, 120, 140, 189, 32, 87, 75, 10, 212, 46, 79, 76, 137, 104, 115, 219, 128, 220, 122, 136, 176, 40, 145, 242, 190, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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