Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a8ab8fb869c6aeac566d4d06310c14a3381248221b99788742f7baeb3ce4962

Tx prefix hash: 0a9ec8eba2db33425fc8051a444fc7c52fa8d60def5aa4444797f19600340ecf
Tx public key: 4a71b7f8aa47ce4fa39f312e0fb8420696a320695afe4ee3f59258d265ca207c
Timestamp: 1729591440 Timestamp [UCT]: 2024-10-22 10:04:00 Age [y:d:h:m:s]: 00:142:00:52:14
Block: 1137044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101312 RingCT/type: yes/0
Extra: 014a71b7f8aa47ce4fa39f312e0fb8420696a320695afe4ee3f59258d265ca207c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 026d81130ee77be1063fd64a5c606c0cb81e6cc1ccb1f7d9c847b947117961a0 0.600000000000 1620461 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": 1137054, "vin": [ { "gen": { "height": 1137044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "026d81130ee77be1063fd64a5c606c0cb81e6cc1ccb1f7d9c847b947117961a0" } } ], "extra": [ 1, 74, 113, 183, 248, 170, 71, 206, 79, 163, 159, 49, 46, 15, 184, 66, 6, 150, 163, 32, 105, 90, 254, 78, 227, 245, 146, 88, 210, 101, 202, 32, 124, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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