Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a450e4fa7450d76a57a9900f9ca3db41f737163ea7a23670a3d9c5337bab749

Tx prefix hash: bebb122c5611f9a3d9d60bccfd89d6aa57cd3aeaf0d0ab63c5631407ad8d956e
Tx public key: f82e07ec17138cb071bd4e3dc70a06d83cbf19dc3c6e121c23880a50c0d9ef19
Timestamp: 1697303353 Timestamp [UCT]: 2023-10-14 17:09:13 Age [y:d:h:m:s]: 01:033:07:16:05
Block: 869588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285022 RingCT/type: yes/0
Extra: 01f82e07ec17138cb071bd4e3dc70a06d83cbf19dc3c6e121c23880a50c0d9ef19021100000006faf35c9c000000000000000000

1 output(s) for total of 0.806666461000 dcy

stealth address amount amount idx
00: 0d195bea8877d30e47874cb722314fd7d259d8af9211319e90f821281d7f2aec 0.806666461000 1324437 of 0

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": 869598, "vin": [ { "gen": { "height": 869588 } } ], "vout": [ { "amount": 806666461, "target": { "key": "0d195bea8877d30e47874cb722314fd7d259d8af9211319e90f821281d7f2aec" } } ], "extra": [ 1, 248, 46, 7, 236, 23, 19, 140, 176, 113, 189, 78, 61, 199, 10, 6, 216, 60, 191, 25, 220, 60, 110, 18, 28, 35, 136, 10, 80, 192, 217, 239, 25, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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