Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 060549689ee95a264fbef2c548b18aa5ad3131d5571623fc1c1c23ea3c55fa97

Tx prefix hash: a7c5689809c221c457adf14e9957691b68ea1a8ad33d2b8711deaaf801fe7927
Tx public key: e45f35eb3f7746fcb8b520299413e2df1c241aacf7195986af3ef58e4fdaf0c5
Timestamp: 1723796292 Timestamp [UCT]: 2024-08-16 08:18:12 Age [y:d:h:m:s]: 01:083:23:39:28
Block: 1089026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318489 RingCT/type: yes/0
Extra: 01e45f35eb3f7746fcb8b520299413e2df1c241aacf7195986af3ef58e4fdaf0c5021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c2e588912d22bc79453eff77288a8344aed43341829fd603dac805e06f4bfc0 0.600000000000 1563645 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": 1089036, "vin": [ { "gen": { "height": 1089026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c2e588912d22bc79453eff77288a8344aed43341829fd603dac805e06f4bfc0" } } ], "extra": [ 1, 228, 95, 53, 235, 63, 119, 70, 252, 184, 181, 32, 41, 148, 19, 226, 223, 28, 36, 26, 172, 247, 25, 89, 134, 175, 62, 245, 142, 79, 218, 240, 197, 2, 17, 0, 0, 0, 8, 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