Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59e1f6e39363f4adf6a8d92569da3e46600c16579f61d8de08c686ecf8d00c9c

Tx prefix hash: 3349f2228b2b2675a6b41d8ba2e07231f7c4f499ae45fdfb7bddc54d52a3fd2d
Tx public key: cd7f2ef94bd780fd071ffeec3d2be00905e2716152877d84b17f3107a25626b3
Timestamp: 1749860890 Timestamp [UCT]: 2025-06-14 00:28:10 Age [y:d:h:m:s]: 00:157:17:23:06
Block: 1304473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110500 RingCT/type: yes/0
Extra: 01cd7f2ef94bd780fd071ffeec3d2be00905e2716152877d84b17f3107a25626b30211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 772ad78afee19a816a35e8a02e6aefdbea4da23cb0b981d878fd268b4f137a95 0.600000000000 1792062 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": 1304483, "vin": [ { "gen": { "height": 1304473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "772ad78afee19a816a35e8a02e6aefdbea4da23cb0b981d878fd268b4f137a95" } } ], "extra": [ 1, 205, 127, 46, 249, 75, 215, 128, 253, 7, 31, 254, 236, 61, 43, 224, 9, 5, 226, 113, 97, 82, 135, 125, 132, 177, 127, 49, 7, 162, 86, 38, 179, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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