Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c87fa8611bb9c88cc542ccf38c44652e799ae1deaa7f784ea16f4484c954e25

Tx prefix hash: 882296233987c0f5cd0d7aaef4eeafdeacf4cffd84b574a492a04409680a122e
Tx public key: 8d2a2429711bb4373a7f8c41eebb6f5bd476b3a4a346a0580e12c4349a1e100f
Timestamp: 1751170541 Timestamp [UCT]: 2025-06-29 04:15:41 Age [y:d:h:m:s]: 00:192:07:50:03
Block: 1314958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135648 RingCT/type: yes/0
Extra: 018d2a2429711bb4373a7f8c41eebb6f5bd476b3a4a346a0580e12c4349a1e100f021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a23ff4b7737ddcf4054f8516769d7e994aa4cf143a60e2fc4f1f6ef01200c02 0.600000000000 1802611 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": 1314968, "vin": [ { "gen": { "height": 1314958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a23ff4b7737ddcf4054f8516769d7e994aa4cf143a60e2fc4f1f6ef01200c02" } } ], "extra": [ 1, 141, 42, 36, 41, 113, 27, 180, 55, 58, 127, 140, 65, 238, 187, 111, 91, 212, 118, 179, 164, 163, 70, 160, 88, 14, 18, 196, 52, 154, 30, 16, 15, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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