Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34c9622c17a976fa15bd912cb926f1b6562e92412852ebaed6d3ffc9030c2e6c

Tx prefix hash: ab95a276b52463d604bce102224598fdc2b23434f95588f1f0d15b5f0fed8873
Tx public key: 6ac111c15f3ab2a1b72d8947387f5df17e7f00a2e70d799fb06352d0ace46fc7
Timestamp: 1768505569 Timestamp [UCT]: 2026-01-15 19:32:49 Age [y:d:h:m:s]: 00:015:09:44:00
Block: 1456407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10984 RingCT/type: yes/0
Extra: 016ac111c15f3ab2a1b72d8947387f5df17e7f00a2e70d799fb06352d0ace46fc702110000000849d73e98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba9231862b490a211f5f89bdccc021060f6d7a466debf8560922abed1b154de3 0.600000000000 1945517 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": 1456417, "vin": [ { "gen": { "height": 1456407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba9231862b490a211f5f89bdccc021060f6d7a466debf8560922abed1b154de3" } } ], "extra": [ 1, 106, 193, 17, 193, 95, 58, 178, 161, 183, 45, 137, 71, 56, 127, 93, 241, 126, 127, 0, 162, 231, 13, 121, 159, 176, 99, 82, 208, 172, 228, 111, 199, 2, 17, 0, 0, 0, 8, 73, 215, 62, 152, 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