Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02aa54c8a959e72dd3808cf023f611bd8bb00021b03947517b26e7a68c090cb7

Tx prefix hash: 8aa279e8a80e2cfdbb7c5580f2a04c7c17bb281369a882c0eba42f67765861d8
Tx public key: bcbcd82118ca41856928e21d32af25d6c9c7b4a9168cc2e8e65d401540f6850c
Timestamp: 1755945265 Timestamp [UCT]: 2025-08-23 10:34:25 Age [y:d:h:m:s]: 00:095:03:44:13
Block: 1352636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67952 RingCT/type: yes/0
Extra: 01bcbcd82118ca41856928e21d32af25d6c9c7b4a9168cc2e8e65d401540f6850c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f1e85a0061a24aa5d15af6742c6de054835710931b782be8657425de43d115 0.600000000000 1840603 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": 1352646, "vin": [ { "gen": { "height": 1352636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f1e85a0061a24aa5d15af6742c6de054835710931b782be8657425de43d115" } } ], "extra": [ 1, 188, 188, 216, 33, 24, 202, 65, 133, 105, 40, 226, 29, 50, 175, 37, 214, 201, 199, 180, 169, 22, 140, 194, 232, 230, 93, 64, 21, 64, 246, 133, 12, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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