Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b169542ab626cba59530eea7178e8e55e08b00a905edf72dfa0f1ca7f6ddd113

Tx prefix hash: 50e46863dffcf1f4df22a3913b664836840a2f8d220f3f13298bce4a522efb18
Tx public key: 9725f0ee5b2eb0eb1f1ae9f1e20bb5a74c5dc968615032fa106598b63e59419a
Timestamp: 1750439303 Timestamp [UCT]: 2025-06-20 17:08:23 Age [y:d:h:m:s]: 00:214:15:44:56
Block: 1309187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151192 RingCT/type: yes/0
Extra: 019725f0ee5b2eb0eb1f1ae9f1e20bb5a74c5dc968615032fa106598b63e59419a021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2485fa810163b99ab579ec21d4ec50e89f6eec2ae5a60429ac828b39732b0e1d 0.600000000000 1796802 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": 1309197, "vin": [ { "gen": { "height": 1309187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2485fa810163b99ab579ec21d4ec50e89f6eec2ae5a60429ac828b39732b0e1d" } } ], "extra": [ 1, 151, 37, 240, 238, 91, 46, 176, 235, 31, 26, 233, 241, 226, 11, 181, 167, 76, 93, 201, 104, 97, 80, 50, 250, 16, 101, 152, 182, 62, 89, 65, 154, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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