Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cba4633b019f38c4046c7b646a0eae6140b22bf66062b37494f29d01f3d8020

Tx prefix hash: 606bbb81b8f3cd0f9bd9594feb1c5950ae56fcec1e6c08556c78e08b5297ecfd
Tx public key: b2482b692d0b41f5d90eb228726c848bd74561a60a456d15333c8cb87e1c0cc5
Timestamp: 1756103217 Timestamp [UCT]: 2025-08-25 06:26:57 Age [y:d:h:m:s]: 00:088:01:18:27
Block: 1353949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62851 RingCT/type: yes/0
Extra: 01b2482b692d0b41f5d90eb228726c848bd74561a60a456d15333c8cb87e1c0cc50211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20abb7f6b69aaf3fc15e18de620a552a87594674f50156892d9eaad261109581 0.600000000000 1841928 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": 1353959, "vin": [ { "gen": { "height": 1353949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20abb7f6b69aaf3fc15e18de620a552a87594674f50156892d9eaad261109581" } } ], "extra": [ 1, 178, 72, 43, 105, 45, 11, 65, 245, 217, 14, 178, 40, 114, 108, 132, 139, 215, 69, 97, 166, 10, 69, 109, 21, 51, 60, 140, 184, 126, 28, 12, 197, 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