Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb59d26b3fe810d13f5c1ddb9a738b29316ea126ffc80bc0f7c24597a29cf6a3

Tx prefix hash: 9f002f61d47415fc8af0b969e5299f4ab6442ecfcbd273ed9144f8cf40ac426f
Tx public key: 01da32c53b7dcfaf64ef7c0d41288ca54efdc8f035a494bd820eee003f0c9235
Timestamp: 1755651411 Timestamp [UCT]: 2025-08-20 00:56:51 Age [y:d:h:m:s]: 00:098:15:20:30
Block: 1350229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70426 RingCT/type: yes/0
Extra: 0101da32c53b7dcfaf64ef7c0d41288ca54efdc8f035a494bd820eee003f0c9235021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9119383ea78d36bce5a2e7c86f7505d1e8780ab07c120e0e0e1467cb98f404c5 0.600000000000 1838170 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": 1350239, "vin": [ { "gen": { "height": 1350229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9119383ea78d36bce5a2e7c86f7505d1e8780ab07c120e0e0e1467cb98f404c5" } } ], "extra": [ 1, 1, 218, 50, 197, 59, 125, 207, 175, 100, 239, 124, 13, 65, 40, 140, 165, 78, 253, 200, 240, 53, 164, 148, 189, 130, 14, 238, 0, 63, 12, 146, 53, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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