Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d295594f0f2d97cc5c8b65f634aa5a0bfc5bdae12debdac0ff84857244a7f8a1

Tx prefix hash: 07426751f84e3a68292e075384ade22924ae8cd7a3209c3df229d863b73f8df9
Tx public key: c0dedd9374d09f0d6a30f8d038006bf86cba73af9b34d73cdc80a5650a467c3d
Timestamp: 1715478783 Timestamp [UCT]: 2024-05-12 01:53:03 Age [y:d:h:m:s]: 00:342:02:44:02
Block: 1020105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244511 RingCT/type: yes/0
Extra: 01c0dedd9374d09f0d6a30f8d038006bf86cba73af9b34d73cdc80a5650a467c3d021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13832d726522f49205c4dcd025b7e3115b3078a83ab286740e3defbe48564612 0.600000000000 1484164 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": 1020115, "vin": [ { "gen": { "height": 1020105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13832d726522f49205c4dcd025b7e3115b3078a83ab286740e3defbe48564612" } } ], "extra": [ 1, 192, 222, 221, 147, 116, 208, 159, 13, 106, 48, 248, 208, 56, 0, 107, 248, 108, 186, 115, 175, 155, 52, 215, 60, 220, 128, 165, 101, 10, 70, 124, 61, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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