Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0cf673bc7ba671174d954ff907466f4f7f69a2165f4cf8cd4c8de9cf90a8c1

Tx prefix hash: 5a157fcf0e7b466a5ccf138e4711b46a2c6b11f6efd8b3e338337a64b712cdd6
Tx public key: 073a28619b73e0e2c1d29214346fd97eacd8cc1fa042eafdc525e1e4e2d72d39
Timestamp: 1756363454 Timestamp [UCT]: 2025-08-28 06:44:14 Age [y:d:h:m:s]: 00:152:16:59:25
Block: 1356103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108975 RingCT/type: yes/0
Extra: 01073a28619b73e0e2c1d29214346fd97eacd8cc1fa042eafdc525e1e4e2d72d390211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65249fa5e61cb9cfb9a36140df0f6897e28485c1b0d511253342881fd655cd7f 0.600000000000 1844108 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": 1356113, "vin": [ { "gen": { "height": 1356103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65249fa5e61cb9cfb9a36140df0f6897e28485c1b0d511253342881fd655cd7f" } } ], "extra": [ 1, 7, 58, 40, 97, 155, 115, 224, 226, 193, 210, 146, 20, 52, 111, 217, 126, 172, 216, 204, 31, 160, 66, 234, 253, 197, 37, 225, 228, 226, 215, 45, 57, 2, 17, 0, 0, 0, 2, 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