Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2c8b727c73f1254c11be238ee562b4c75c1ae70b462fc6209996b52f5d73273

Tx prefix hash: 26d62186bf5550fbb09490e7307d54803bd019142e0e9a5fd6eae939813233be
Tx public key: 057b13eb49e7eda70b7279a279f398430e7e24f8c7a00158a79bd09ed612eb77
Timestamp: 1736508896 Timestamp [UCT]: 2025-01-10 11:34:56 Age [y:d:h:m:s]: 00:089:19:17:11
Block: 1194275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63976 RingCT/type: yes/0
Extra: 01057b13eb49e7eda70b7279a279f398430e7e24f8c7a00158a79bd09ed612eb77021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38ee22c1ad832d13aae03eec6c489696f8d2ea626b37014bd2b0b38a34a9f7a0 0.600000000000 1680844 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": 1194285, "vin": [ { "gen": { "height": 1194275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38ee22c1ad832d13aae03eec6c489696f8d2ea626b37014bd2b0b38a34a9f7a0" } } ], "extra": [ 1, 5, 123, 19, 235, 73, 231, 237, 167, 11, 114, 121, 162, 121, 243, 152, 67, 14, 126, 36, 248, 199, 160, 1, 88, 167, 155, 208, 158, 214, 18, 235, 119, 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