Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da6745b33f435337c0d671c56074dcc9918cefd9ec1994ed9da274f4645aa431

Tx prefix hash: e537353c6848e4a81a2347e3b6a4b34b89d93037c6a9bccbe56c3feaa423333b
Tx public key: f456cb830bc65bbdefd3d80511cc18c57f64d4e5c6925abe0180178c02f9d876
Timestamp: 1745344902 Timestamp [UCT]: 2025-04-22 18:01:42 Age [y:d:h:m:s]: 00:211:14:17:21
Block: 1267162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148951 RingCT/type: yes/0
Extra: 01f456cb830bc65bbdefd3d80511cc18c57f64d4e5c6925abe0180178c02f9d8760211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14f0ff13f3dceca942b77f1cd28f7a5bb784f7d97da9217afe3037c59eaa1300 0.600000000000 1754389 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": 1267172, "vin": [ { "gen": { "height": 1267162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14f0ff13f3dceca942b77f1cd28f7a5bb784f7d97da9217afe3037c59eaa1300" } } ], "extra": [ 1, 244, 86, 203, 131, 11, 198, 91, 189, 239, 211, 216, 5, 17, 204, 24, 197, 127, 100, 212, 229, 198, 146, 90, 190, 1, 128, 23, 140, 2, 249, 216, 118, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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