Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd579f88e92198f0e0e3041c3fc8ee280999ca72807faae29b92488a5993ae5b

Tx prefix hash: a4f12e4d9ca2858ac2d383b1079d8ecd0e0a586a2c1900ab9ea309a837834b40
Tx public key: 31ae00a7607aa9774b5f1d489cfac7af51ee96116e6d26eaef2041c1f1311ef1
Timestamp: 1753010266 Timestamp [UCT]: 2025-07-20 11:17:46 Age [y:d:h:m:s]: 00:118:23:24:47
Block: 1329482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83840 RingCT/type: yes/0
Extra: 0131ae00a7607aa9774b5f1d489cfac7af51ee96116e6d26eaef2041c1f1311ef1021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b729237ad5811ecdf441eec78bfbf3d14daa2e3cc695e96e46bdae0dd0c2cb7 0.600000000000 1817259 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": 1329492, "vin": [ { "gen": { "height": 1329482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b729237ad5811ecdf441eec78bfbf3d14daa2e3cc695e96e46bdae0dd0c2cb7" } } ], "extra": [ 1, 49, 174, 0, 167, 96, 122, 169, 119, 75, 95, 29, 72, 156, 250, 199, 175, 81, 238, 150, 17, 110, 109, 38, 234, 239, 32, 65, 193, 241, 49, 30, 241, 2, 17, 0, 0, 0, 1, 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